Recording apparatus, server apparatus, recording method, program, and storage medium

ABSTRACT

A data recording apparatus recording data of a CD on an HDD in a manner such that the content of record in the CD is faithfully accounted for and shortening an operation time for a synchronized ripping operation. When the data recording apparatus reads, from the CD, track data managed by track, according to TOC, and records the track data onto the HDD, the data recording apparatus recognizes data unrecorded on the HDD, from among the track data recorded on the CD. This recognition process is automatically performed based on the TOC read from the CD, and album information replayed using the TOC and held by the HDD. The recording apparatus reproduces and outputs only the unrecorded data from the CD based on the recognition result concerning the unrecorded data. In this way, the data already recorded on the HDD is not transferred from the CD to the HDD. The operation time for the synchronized ripping operation is reduced accordingly.

This is a continuation of application Ser. No. 10/484,633, filed Jan.23, 2004, now U.S. Pat No. 7,145,741, the entire contents of which ishereby incorporated by reference.

The present application claims priority based on Japanese PatentApplication No. 2002-170901, filed Jun. 12, 2002 with the National Phaserelating to PCT/JP03/07411, filed Jun. 11, 2003, the entirety of whichis being incorporated herein by reference.

TECHNICAL FIELD

The present invention relates to a recording apparatus that records,onto one recording medium, data recorded on another recording medium ofa particular type, and managed by program, and a server apparatus thatis able to download data to the recording apparatus connected thereto.The present invention also relates to a recording method for therecording apparatus, a program for embodying the recording apparatus andthe recording method, and a recording medium storing the program.

BACKGROUND ART

Low-cost and large-capacity hard disks are currently in widespread use.One currently widely accepted practice is that audio data is compressedand recorded using the MP3 (MPEG Audio Layer III) method and the ATRAC(Adaptive Transform Acoustic Coding) method.

Along with this trend, so-called ripping is widely accepted. In theripping operation, audio data recorded on a CD (Compact Disk) iscompressed and recorded onto a hard disk for storage. The rippingoperation is performed by personal computers, for example. Audioequipment may be supplied with a disk drive replaying the CD and a harddisk attached thereon. Such audio equipment may also perform the rippingoperation.

If audio data such as a great deal of musical compositions is storedonto a hard disk through the ripping operation, a user is freed frominconveniences, such as replacing one CD with another CD having an albumthe user desires most to listen to, and enjoys music listeningenvironment more than before.

When all content of the album of the CD, namely, all tracks (programs)recorded on the CD, are ripped in the ripping operation, all tracksrecorded on the CD, which is a rip source, are unconditionallytransferred to a hard disk for recording. In the discussion thatfollows, the term synchronized ripping refers to the recording of thetracks on the hard disk that is performed in synchronization with thecontent of the CD when all content of the album of the CD is transferredto the hard disk in the ripping operation.

Data is managed by program in media such as the CD. The programtypically refers to as a track. In the description of this embodiment,the program recorded on the CD is also referred to as the track.

When the user rips data from a CD, music of some tracks only isfrequently ripped from the CD.

For example, the user now desires to rip all tracks of the CD, fromwhich the user has already ripped some tracks, and performs synchronizedripping on the CD.

In the CD synchronized ripping, as already discussed, all tracksrecorded on the CD are unconditionally transferred to the hard disk forrecording. Some tracks, which have already ripped, from among all tracksthat are going to be ripped this time, are duplicated in the recordingon the hard disk.

If the same tracks are duplicated on the hard disk, the capacity of thehard disk is consumed in vain. In other words, data that is alreadystored through a ripping operation is preferably prevented from beingduplicated in the recording on the hard disk.

Another drawback is discussed below.

Time required to rip one CD is several minutes to tens of minutesdepending on performance of a ripping system and replay time of the CD,and is not a short period of time. Time required to rip the CD ispreferably shortened as much as possible.

If the ripping operation is performed in the CD synchronized rippingmethod, all tracks are replayed from the CD, and are transferred to thehard disk for recording. This means that tracks ripped in the past,expected to be duplicated, are also transferred from the CD to the harddisk.

The tracks that are going to be recorded in duplication are replayedfrom the CD and recorded on the hard disk. Ripping time is prolonged invain accordingly. The CD synchronized ripping operation is notsufficient from the standpoint of fast operation.

To prevent the tracks from being recorded on the hard disk induplication in the above-referenced CD synchronized ripping operation, auser must select tracks to be ripped from the tracks recorded on the CDbefore the ripping operation.

To select tracks, the user first must check to see whether the tracksrecorded on the rip source CD are duplicated on the hard disk.

To check a duplication, the user must be provided with a user interfacethat allows the user to visually recognize the content of the tracksrecorded on the CD and the content of the tracks currently recorded onthe hard disk as a result of ripping. Such a user interface is typicallyavailable in the ripping system using a personal computer.

The user thus recognizes already ripped tracks using a system such asthe above-mentioned personal computer. Dedicated ripping apparatusestypically have a small display on the body thereof, and it is notpractical for the dedicated ripping apparatus to present the display ofa track recorded on the rip source CD and a track already recorded onthe hard disk. In this case, the user must replay the tracks recorded onthe CD and the hard disk to check the duplication. Such an operation isinconvenient to the user.

The system such as the personal computer is usable, but the user muststill perform a operation particular for checking and ease of use is notprovided.

DISCLOSURE OF INVENTION

In view of the above drawback, it is an object of the present inventionto provide a high-speed ripping technique in which when data that isrecorded on a storage medium such as a CD by track (program) is ripped,already ripped tracks are not ripped in duplication.

To provide the high-speed ripping technique, the ripping operation isperformed after the already ripped tracks are automatically recognized.The user thus enjoys the ease of use in the ripping operation.

To this end, a recording apparatus has the following structure.

The recording apparatus includes data reading means that reads, from afirst recording medium that stores data and first management data formanaging the data by program, the first management data and the data byprogram, recording means that records, onto a second recording medium,the data by program read by the data reading means, management dataproducing means that produces second management data that manages thedata by program recorded on the second recording medium and the firstmanaging data which is considered as being read and acquired by the datareading means from the first recording medium that has stored the databy program, with the data by program associated with the firstmanagement data, unrecorded program determining means that determinesdata by program considered as being unrecorded on the second recordingmedium, from among data by program stored in the first recording mediumand to be read by the data reading means, by comparing the firstmanagement data read by the data reading means with the informationcontent of the second management data, and control means that performs acontrol process to cause the data reading means to read the unrecordeddata by program based on the determination result provided by theunrecorded program determining means, and to cause the recording meansto record the unrecorded data by program read by the data reading meansonto the second recording medium.

A server apparatus has the following structure.

The server apparatus is based on the assumption that a storage medium,as an album, storing data and management data for managing the data byprogram is present.

The server apparatus includes download data storage means that stores,as download data, data by program as the album, and the management datarecorded on the storage medium as the album, data reading means thatreads, from the download data storage means, data requested by program,and management data that is considered as being recorded on the storagemedium as the album that stores the data by program, when thedownloading of the data by program is requested through a network, andtransmitting means that transmits, to the recording apparatus, the databy program and the management data read by the data reading means.

A recording method includes the following steps.

The data recording method includes a data reading step for reading, froma first recording medium that stores data and first management data formanaging the data by program, the first management data and the data byprogram, a recording step for recording, onto a second recording medium,the data by program read in the data reading step, a management dataproducing step for producing second management data that manages thedata by program recorded on the second recording medium and the firstmanaging data which is considered as being read and acquired in the datareading step from the first recording medium that has stored the data byprogram, with the data by program associated with the first managementdata, an unrecorded program determining step for determining data byprogram considered as being unrecorded on the second recording medium,from among data by program stored on the first recording medium and tobe read in the data reading step, by comparing the first management dataread in the data reading step with the information content of the secondmanagement data, and a control step for performing a control process toread the unrecorded data by program in the data reading step based onthe determination result provided in the unrecorded program determiningstep, and to record, in the recording step, the unrecorded data byprogram read in the data reading step onto the second recording medium.

A program includes the following processes.

The program causes the recording apparatus to perform a data readingprocess for reading, from a first recording medium that stores data andfirst management data for managing the data by program, the firstmanagement data and the data by program, a recording process forrecording, onto a second recording medium, the data by program read inthe data reading process, a management data producing process forproducing second management data that manages the data by programrecorded on the second recording medium and the first managing datawhich is considered as being read and acquired in the data readingprocess from the first recording medium that has stored the data byprogram, with the data by program associated with the first managementdata, an unrecorded program determining process for determining data byprogram considered as being unrecorded on the second recording medium,from among data by program stored on the first recording medium and tobe read in the data reading process, by comparing the first managementdata read in the data reading process with the information content ofthe second management data, and a control process for reading theunrecorded data by program in the data reading process based on thedetermination result provided in the unrecorded program determiningprocess, and for recording, in the recording process, the unrecordeddata by program read in the data reading process onto the secondrecording medium.

A storage medium is constructed as below.

The storage medium causes the recording apparatus to perform a datareading process for reading, from a first recording medium that storesdata and first management data for managing the data by program, thefirst management data and the data by program, a recording process forrecording, onto a second recording medium, the data by program read inthe data reading process, a management data producing process forproducing second management data that manages the data by programrecorded on the second recording medium and the first managing datawhich is considered as being read and acquired in the data readingprocess from the first recording medium that has stored the data byprogram, with the data by program associated with the first managementdata, an unrecorded program determining process for determining data byprogram considered as being unrecorded on the second recording medium,from among data by program stored on the first recording medium and tobe read in the data reading process, by comparing the first managementdata read in the data reading process with the information content ofthe second management data, and a control process for reading theunrecorded data by program in the data reading process based on thedetermination result provided in the unrecorded program determiningprocess, and for recording, in the recording process, the unrecordeddata by program read in the data reading process onto the secondrecording medium.

In each of the above arrangements, the data by program and the firstmanagement data for managing the data by program are stored in the firststorage medium as a rip source. With the server apparatus in use, thefirst management data is acquired from the server apparatus duringdownloading of data.

When the data of programs read from the first storage medium is recordedonto the second storage medium as a rip destination, the secondmanagement data is produced in a manner such that the data of programsrecorded on the second storage medium is associated with the programmanaged by the first management data. The second management data allowsthe user to recognize the data of programs already recorded on thesecond storage medium and data of unrecorded programs from among thedata of the programs recorded on the first storage medium.

To perform a replay for ripping in response to the result ofrecognition, only the data of programs unrecorded on the second storagemedium are selected from the first storage medium and replayed to recordthe unrecorded programs on the second storage medium. Based on thesecond management data, the data of the programs already recorded on thesecond storage medium is not replayed from the first storage medium, andnot ripped onto the second storage medium.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram illustrating the structure of a ripping systemapparatus of one embodiment of the present invention.

FIG. 2 diagrammatically illustrates a CD synchronized ripping operationof the present embodiment.

FIGS. 3A through 3D illustrate a display example of ripping state.

FIGS. 4A through 3D illustrate another display example of the rippingstate.

FIG. 5 illustrates the structure of a ripping database.

FIG. 6 illustrates the structure of a ripped file table.

FIG. 7 illustrates the structure of album information.

FIG. 8 illustrates the structure of a CD-TOC table.

FIG. 9 illustrates the structure of a ripping state table.

FIG. 10 illustrates the structure of a title table.

FIG. 11 is a flowchart of a process of the ripping system apparatus ofthe present embodiment before a ripping state of a CD is recognized.

FIG. 12 is a flowchart of a process of the ripping system apparatus ofthe present embodiment illustrating the execution of the synchronizedripping operation.

FIG. 13 is a flowchart illustrating a process in which a registrationoperation for registering a track title corresponding to newly recordedripped data is performed.

FIG. 14 is a block diagram illustrating the structure of a downloadserver of the present embodiment.

FIG. 15 is a flowchart illustrating the process of a download operationperformed between the download server and the ripping system apparatus.

FIG. 16 illustrates a frame structure of a CD.

FIGS. 17A and 17B illustrate sub-coding of the CD.

FIGS. 18A and 18B illustrate sub Q data of the CD.

FIG. 19 illustrates TOC data of the CD.

BEST MODE FOR CARRYING OUT THE INVENTION

The embodiments of the present invention will now be discussed in theorder listed below.

1. Construction of Ripping System Apparatus

2. TOC and Sub Code of CD

3. Outline of the Operation of the Ripping System Apparatus

4. Ripping State Display

5. Structure of Ripping Database

6. Process of CD Synchronized Ripping

7. Cooperative Operation with Download Server

1. Construction of Ripping System Apparatus

FIG. 1 is a block diagram illustrating the internal structure of aripping system apparatus 1 as a recording apparatus in one embodiment ofthe present invention. In a ripping process, the ripping systemapparatus 1 compresses digital audio data (hereinafter also referred toas track data) replayed from a CD by track using a predetermined digitalaudio data compression method and records the compressed track data ontoa hard disk (HDD).

As shown in FIG. 1, the ripping system apparatus 1 of the presentembodiment includes, as major elements thereof, a CD section 2, a harddisk drive (HDD) section 3, and a user interface section 4. The rippingsystem apparatus 1 also includes an audio signal output section 5 foroutputting audio data, replayed by the CD section 2 or the HDD section3, as an analog audio signal. Also included is a network interface 36for connection with a network such as the Internet.

The CD section 2 is discussed first.

A CD 10 is loaded into the CD section 2. A CD driver 11 reads a signalfrom the CD 10 loaded in the CD section 2. As is well known, a laserlight beam is directed to a signal surface of the CD with the CD 10rotated by a CLV, for example, to read the signal from the CD. Signalreading is performed by detecting the reflected laser light beam.

A signal read by the CD driver 11 is input to a signal processor circuit12. The signal read by the CD driver 11 is an RF signal. The signalprocessor circuit 12 generates a replayed RF signal and various servocontrol signals from the input RF signal.

The replayed RF signal is converted into 16 bit sampled digital audiodata having a sampling frequency of 44.1 kHz through an EFM demodulationprocess, an error correction process, etc.

The digital audio data thus obtained is transferred to a signalprocessor circuit 22 in the HDD section 3 during a ripping operation.The digital audio signal, output to an audio signal output section 5, issubjected to required signal processes including a D/A conversionprocess, and amplification, and is then output to an audio outputterminal 5 a as an analog audio signal for an L/R stereo. The sameoutput is applied to a headphone output terminal 5 b.

A servo signal processing system is not shown here. With the variousservo error signals extracted from the RF signal being fed back, the CDdriver 11 side performs tracking servo control, focusing servo control,spindle motor rotation control, etc., as is known in the art.

A lead-in area of the CD records a TOC (Table Of Contents) representingthe record content of the CD through sub-coding, as is well known. Thesignal processor circuit 12 extracts a sub code from the decoded digitalaudio data, and transfers the extracted sub code to the CD controller14. In this way, information of the TOC recorded on the lead-in area asthe sub code is extracted by the signal processor circuit 12, and isthen acquired by the CD controller 14.

The CD-DA format permits text data to be recorded through sub coding.The text data typically includes, an album title as an album for the CD,title information concerning each track, information relating to thename of an artist, and is recorded in an ASCII code text data format.

The present embodiment includes a text decoder 13 for the text data.

The text decoder 13 is designed to receive a sub code extracted by thesignal processor circuit 12, and extract text data from the input subcode. The CD controller 14 performs decode control so that the textdecoder 13 acquires desired text data from a group of text data. Thetext data obtained in this way is written onto an RAM 16 for storageunder the control of the CD controller 14.

The text data held in the RAM 16 is used in the following way in thepresent embodiment, for example.

For example, when the CD 10 is replayed on the CD section 2, informationdisplayable by the text data, such as an album title of the CD 10 and atitle of a track under replay, is displayed as a text on a display unit35 as appropriate.

The CD controller 14 monitors the current operational status of the CDsection 2, and waits on standby until a UI controller 31 sends a commandfor updating a display mode in response to an operation of an operationunit 34. The CD controller 14 reads required text data from the RAM 16in response to the operational status and the command, and outputs thetext data to the UI controller 31 through a system bus 37. The UIcontroller 31 displays the received and input text data on the displayunit 35 as characters.

In the present embodiment, the digital audio data by track recorded onthe CD 10 is subjected to a compression process, and is then recorded asa ripped file 20A on a hard disk 20. In this way, a so-called rippingoperation for ripping data from the CD to the hard disk is performed.

The text data recorded on the CD 10 in the present embodiment isrecorded onto the hard disk 20 as additional information concerning theripped file 20A.

It is now assumed that the track replayed from the CD 10 in the rippingoperation is recorded on the hard disk 20 as the ripped file 20A. The CDcontroller 14 then sends, to an HDD controller 25, the text datarepresenting the album title of the CD on which the ripped track isconsidered as being recorded, and the title of the track.

The HDD controller 25 stores the transferred text data representing thealbum title and the track title in a ripping database 20B to bediscussed later with the ripped file 20A associated with the text data.

In this arrangement, as long as the text data is stored on the ripsource CD 10, information about the album title and the track title ofthe ripped file 20A is acquired from the text without the need for theuser to perform an input operation.

When a replay list of the ripped files 20A is displayed or replayed foroutput, the display unit 35 displays the title of the album to which theripped file 20A belongs, and the title of a musical composition of theripped file 20A. In a display control process of the display unit 35,the HDD controller 25 reads desired text data from the ripping database20B and transfers the text data to the UI controller 31 through thesystem bus 37. The UI controller 31 controls the display unit 35 todisplay the transferred text data as characters.

The CD controller 14 in the CD section 2 includes a CPU, for example,and controls the operation of the CD section 2. The CD controller 14 isalso able to communicate, through the system bus 37, with the HDDcontroller 25 of the HDD section 3 to be discussed later and the UIcontroller 31 of the user interface section 4.

The CD controller 14 includes an ROM 15 and an RAM 16. The ROM 15 storesa program to be executed by the CD controller 14, and various settinginformation. The RAM 16 serves as a working area the CD controller 14uses in the control process thereof, and holds various data the CDcontroller 14 temporarily needs to execute the control process.

The HDD section 3 is discussed below.

The signal processor circuit 22 in the HDD section 3 receives thedigital audio data which has been replayed from the CD 10 for rippingand sent from the signal processor circuit 12 in the CD section 2 asdescribed above.

The signal processor circuit 22 performs a compression process on thedigital audio data coming in from the CD section 2 using a predetermineddigital audio data compression method.

The compressed audio data, obtained as a result of the compressionprocess of the signal processor circuit 22, is output to an HD driver 21as record data to the hard disk 20. The HD driver 21 performs a recordencoding process, appropriate for data writing to the hard disk 20, onthe input compressed audio data, and transfers the processed data to thehard disk 20, and writes the processed data onto the hard disk 20 bydesignating an address thereon. In this way, the digital audio datareplayed from the CD 10 is stored in the hard disk 20 in the compressedform thereof. In other words, the ripping operation has beenaccomplished.

By managing a file system for managing data such as a file recorded onthe hard disk 20, the HD driver 21 appropriately executes a read/writeoperation of data.

The compressed audio data thus stored in the hard disk 20 is to bemanaged as the ripped file 20A as shown. Each ripped file 20Acorresponds to the audio data per track recorded on the CD 10.

The hard disk 20 stores the ripping database 20B as management data formanaging the ripped file stored in the hard disk 20.

In the ripping operation, the HDD controller 25 generates the rippingdatabase 20B in response to the results of ripping, thereby successivelyupdating the ripping database 20B.

The ripping system apparatus 1 in the present embodiment can select anyfile from among the ripped files 20A stored in the hard disk 20 and canreplay the selected file.

In this case, the UI controller 31 issues a replay request afterdesignating the ripped file 20A in response to a replay operation of thedesignated ripped file 20A performed on the operation unit 34 of theuser interface section 4 to be discussed later. When the replay requestreaches the HDD controller 25 through the system bus 37, the HDDcontroller 25 instructs the HD driver 21 to read the designated rippedfile 20A. The HD driver 21 accesses an address having the designatedripped file written thereon on the hard disk 20 to read the data of thefile, and transfers the read data to the signal processor circuit 22.

As already discussed, the ripped file 20A transferred from the HD driver21 is compressed audio data. The signal processor circuit 22, which hasreceived the data of the ripped file 20A, performs, on the data, a datadecompression process corresponding to the above-mentioned audio datacompression method. The signal processor circuit 22 thus converts thedata into digital audio data having a predetermined sample bit andsampling frequency. The resulting signal is then output to the audiosignal output section 5.

As already discussed, the audio signal output section 5 finally outputsthe input digital audio data, as an analog audio signal, to the audiooutput terminal 5 a and the headphone output terminal 5 b.

The ripped file 20A stored in the hard disk 20 can be replayed as anaudio sound.

The HDD controller 25, including a CPU, etc., executes the controlprocess so that the HDD section 3 performs the operation that has beendiscussed.

THE HDD controller 25 also includes an ROM 23 and an RAM 24. The ROM 23stores a program for the control process the HDD controller 25 mustperform. The RAM 24 is a memory serving as a working area of the HDDcontroller 25.

The user interface section 4 will now be discussed.

The user interface section 4 includes the UI (User Interface) controller31 containing a CPU, etc. The UI controller 31 controls the generalfunction of the user interface section 4.

For example, the UI controller 31 converts operation information, outputfrom the operation unit 34 in response to an operation performed on theoperation unit 34, into a command (request information) the CDcontroller 14 and the HDD controller 25 can process, and transfers thecommand, through the system bus 37, to the CD controller 14 or the HDDcontroller 25.

In communication with the CD controller 14 and the HDD controller 25,the UI controller 31 performs display control so that the display unit35 presents a display accounting for a current operational status.

An ROM 32 stores a program to cause the UI controller 31 to execute theoperations of the user interface section 4 including the ones alreadydescribed above, various initial setting information, etc. An RAM 33 isused as a working area for the UI controller 31.

The operation unit 34 includes a variety of controls provided on theapparatus body of the ripping system apparatus 1 in practice, andoutputs an operational signal to the UI controller 31 in response to anactually performed operation on these controls.

In addition to the operation unit 34, one of a wired remote controllerand a wireless remote controller may be used in one arrangement. Thearrangement receives a signal responsive to an operation performed onthe remote controller and outputs the signal to the UI controller 31.

In such a case, the network interface 36 may be connected to the systembus 37. With the network interface 36, the ripping system apparatus 1 ofthe present embodiment is connected to a network.

2. TOC and Sub Code of the CD

As is well known, the TOC is recorded using sub coding data in thelead-in area in the CD 10 (CD-DA) loaded in the CD section 2. The TOCand the sub code, recorded on the lead-in area, are discussed.

A minimum unit of data to be recorded onto the CD-DA is 1 frame. A totalof 98 frames constitute 1 block (1 sub coding frame). The structure of 1frame is shown in FIG. 16.

As shown, 1 frame is formed of 588 bits, leading 24 bits containsynchronization data, and subsequent 14 bits are a sub code data area,followed by data and parities.

One block is formed of 98 frames, each having the above-mentionedstructure. Sub code data extracted from the 98 frames is collected intoone block as listed in FIG. 17A.

The sub code data from a first frame and a second frame of the 98 frames(frame 98 n+1 and frame 98 n+2) has a synchronization pattern. A thirdframe to a 98th frame (frame 98 n+3-frame 98 n+98) form 96 bit channeldata, namely, sub code data of P, Q, R, S, T, U, V, and W.

From among these, the P channel and the Q channel are used to manageaccess, etc. However, the P channel indicates only a pause sectionbetween tracks, and finer control is performed by the Q channel(Q1-Q96). The Q channel data of 96 bits is organized as shown in FIG.7B.

Although the channel data is not discussed in detail, R channel data-Wchannel data are arranged to form text data group. The text decoder 13shown in FIG. 1 extracts the text data, inserted in a predeterminedformat, from the R channel data-W channel data in the decode processthereof.

The text data may contain information such as an album title, a tracktitle, names of players (including the name of a conductor and the nameof an orchestra), the name of a lyric writer, the name of a composer,the name of an adapter, a message, a disk ID, genre, and ISRC. Whichinformation to use may be left to the responsibility of each apparatus.In the present embodiment, at least the album title and the track titleare used to manage the ripped file 20A.

Q1-Q4 of 4 bits, referred to as control data, are used for the number ofaudio channels, emphasis, and the identification of the CD-ROM.

More specifically, the 4 bit control data is defined as below.

“0***” 2 channel audio “1***” 4 channel audio “*0**” CD-DA “*1**” CD-ROM“**0*” digital copying disabled “**1*” digital copying enabled “***0”without pre-emphasis “***1” with pre-emphasis

Q5-Q8 of 4 bits, being an address, are control bits of sub Q data.

The 4 bit address “0001” indicates that sub Q data of subsequent Q9-Q80are audio Q data, and the 4 bit address “0100” indicates that the sub Qdata of the subsequent Q9-Q80 is video Q data.

Q9-Q80 are the sub Q data of 72 bits, and the remaining Q88-Q96 are CRC.

The sub Q data recorded in the lead-in area forms the TOC.

The sub Q data of Q9-Q80 of 72 bits in the Q channel data read from thelead-in area contains information shown in FIG. 18A. Each of the sub Qdata is 8 bit data.

Track numbers are also recorded. The track number in the lead-in area isfixed to “00”.

In succession, POINT is recorded, followed by MIN (minute), and SEC(second), and FRAME (frame number) as time elapse within the track.

PMIN, PSEC, and PFRAME, recorded in succession, have the followingdefinition based on the value of the POINT.

If the value of POINT is within a range of “01h”-“99h” (the letter hrepresents a hexadecimal number), that value represents a track number.In this case, a start point (absolute time address) of a track havingthe track number is recorded as minutes (PMIN), seconds (PSEC), and aframe number (PFRAME) in PMIN, PSEC, and PFRAME.

If the value of POINT is “A0h”, the track number of a first track isrecorded in PMIN. The value of PSEC discriminates between CD-DA, CD-I,and CD-ROM (XA specifications).

If the value of POINT is “A1h”, the track number of last track isrecorded in PMIN.

If the value of POINT is “A2h”, the start point of a lead-out area isindicated as the absolute time address in PMIN, PSEC, and PFRAME.

For example, in a disk with 6 tracks recorded, the data shown in FIG. 19is recorded as the TOC of sub Q data.

As shown, track numbers TNO are all “00h”.

A block NO. represents a number assigned to sub Q data of one unit readas the block data of 98 frames as described above.

The same TOC data is repeated for three consecutive blocks.

As shown, if the value of POINT is within a range of “01h”-“06h”, startpoints of track #1-track #6 are indicated as PMIN, PSEC, and PFRAME.

If the value of POINT is “A0h”, “01” is indicated as a first tracknumber in PMIN. If the disk is discriminated as being the CD-DA byreferring to the value of PSEC, PSEC=“00h” is indicated as shown. In thecase of the CD-ROM (XA specifications), PSEC=“20h” is indicated, and inthe case of the CD-I, PSEC is “10h”.

With the value of POINT at “A1h”, the track number of last track isrecorded in PMIN, and with the value of POINT at “A2h”, the start pointof the lead-out area is indicated in PMIN, PSEC, and PFRAME.

On a block n+27 and subsequent blocks, the content of the block nthrough block n+26 is repeated.

In track #1-track #n and the lead-out area of the disk 1 where data suchas music is actually recorded, the sub Q data recorded there containsinformation of FIG. 18B.

A track number is recorded first. Each of track #1-track #n takes any of“01h”-“99h”. A track number of the lead-out area is “AAh”.

Recorded as an index is information that segments each track.

MIN (minutes), SEC (seconds), and FRAME (frame number) are indicated asthe time elapse within the track.

Absolute time address is recorded as minutes (AMIN), seconds (ASEC), anda frame number (AFRAME) in AMIN, ASEC, and AFRAME.

The TOC and the sub code are organized in this way. It is understoodthat the address on the disk, namely, AMIN, ASEC, and AFRAME arerecorded according to a unit of 98 frames.

The 98 frames (1 block) are referred to as 1 sub coding frame. Sounddata for 1 second contains 75 sub coding frames. More specifically, the“AFRAME” as an address takes a value within a range from “0”-“74”.

3. Outline of the Operation of the Ripping System Apparatus

The CD synchronized ripping operation of the ripping system apparatus 1of the present embodiment illustrated in FIG. 1 will now be discussedwith reference to FIG. 2.

For clarification of discussion, the CD synchronized ripping in thecontext of this description means the recording operation in which databy album of all tracks, with one album corresponding to a single CD, isrecorded onto the hard disk 20 as the ripped file 20A as a result of theripping operation.

FIG. 2 illustrates operational sequences of the CD section 2, the HDDsection 3, and the user interface section 4 from the loading of the CD10 as a rip source into the CD section 2 to the completion of the CDsynchronized ripping of the present embodiment.

As shown in FIG. 2( a), the CD 10 as a rip source is loaded into the CDsection 2. The CD here is a CD(A).

The CD(A) has data of five tracks from Tr1-Tr5 recorded as shown in FIG.2( a). The CD section 2 accesses the lead-in area of the CD(A), therebyreading the TOC. The CD section 2 transfers the content of the TOC tothe HDD section 3. The CD section 2 notifies the HDD section 3 of therecord content of the CD(A).

Upon receiving the record content of the CD(A), the HDD section 3compares the record content of the received TOC with the ripping stateof a ripped file already recorded on the hard disk 20. The ripping stateof the hard disk 20 is learned by referencing the ripping database 20B.The structure of the ripping database 20B will be discussed later.

Based on the results of comparison, the HDD section 3 determines whetherany file of the ripped file 20A currently stored in the hard disk 20 isalready recorded as the file of a track recorded on the CD(A) as acontent. If any ripped file 20A is already recorded, the HDD section 3recognizes which track of the CD(A) the ripped file 20A corresponds to.More specifically, the HDD section 3 recognizes the ripping state withrespect to the tack data of the CD(A).

Referring to FIG. 2( b), the result of recognition indicates that eachof three tracks Tr1, Tr2, and Tr3 of the CD(A) is already stored on thehard disk 20 as the ripped files 20A.

The HDD section 3 notifies the CD section 2 of the recognized rippingstate of the CD(A). Similarly, the HDD section 3 notifies the userinterface section 4 of the ripping state.

The operation of the user interface section 4 responsive to thenotification of the ripping state will be discussed later in connectionwith the “ripping state display”. The operation of the CD section 2notified of the ripping state is discussed first.

Upon receiving the notification of the ripping state concerning theCD(A) as shown in FIG. 2( c), the CD section 2 can recognize which ofthe track data recorded on the CD(A) is unripped and unrecorded trackdata on the hard disk 20. To this end, the CD section 2 must compare thecontent of the TOC read from the CD(A) with the content of the notifiedripping state.

In this case, two tracks Tr2 and Tr4, out of the track data recorded onthe CD(A), are recognized as unrecorded data.

When a command is issued to perform the DC synchronized ripping on thecurrently loaded CD(A), the CD section 2 replays only the data of theunrecorded tracks Tr2 and Tr4 out of the tracks Tr1-Tr5 recorded on theCD(A) as shown in FIG. 2( c), and transfers the data of the unrecordedtracks Tr2 and Tr4 to the HDD section 3.

As is well known, ordinary CD players perform a so-called programmedreplay to replay data on a track selected by a user in a replay orderdesignated by the user. To allow the CD section 2 to replay theunrecorded tracks only as described above, program setting for replay iscontrolled by the CD controller 14, for example, rather than by theuser.

FIG. 2( d) illustrates the operation of the HDD section 3 that hasreceived the replayed data of the tracks Tr2 and Tr4 transferred fromthe CD section 2 as described above. The HDD section 3 compresses thedata of the received tracks Tr2 and Tr4 as described above, andtransfers the compressed data to the hard disk 20 for recording. Thiscompletes the ripping operation of the data of the tracks Tr2 and Tr4replayed from the CD(A).

As a result, as shown in FIG. 2( d), the HDD section 3 has recorded thedata of all tracks Tr1-Tr5 recorded on the CD(A) on the hard disk 20 asthe ripped files 20A. In other words, the files of all tracks formingthe album as the CD(A) are completed as the ripped files 20A stored inthe hard disk 20.

As a result, all data of the tracks by album corresponding to the singleCD is recorded on the hard disk 20 as the ripped files 20A. The CDsynchronized ripping has been normally completed.

In the known art as already discussed, the CD synchronized rippingoperation replays all tracks recorded on the CD and transfers the tracksto the hard disk for recording in an unconditional manner. The CDsynchronized ripping operation duplicates track data if the track datahas already been ripped to the hard disk. Unless the duplicated trackdata is deleted, the capacity of the hard disk is consumed in vain.

When all track data recorded on the CD is unconditionally recorded inthe CD synchronized ripping operation, the track data, already ripped tothe CD from the track data recorded on the CD as a rip source, is alsoreplayed and recorded onto the hard disk. Resulting ripping time becomesuseless.

For example, to overcome this problem, a user has learned a ripped fileexpected to be duplicated by displaying a ripped file list using apowerful GUI of a personal computer, and has set a program for CDreplaying. This process is troublesome to the user.

However, in accordance with the present embodiment, the communication,performed between the CD section 2 and the HDD section 3 as alreadydiscussed with reference to FIG. 2, determines the track data unrecordedas a ripped file from among the track data recorded on the CD as the ripsource.

Based on the result of determination, only the unrecorded track data isreplayed and ripped during CD synchronized ripping.

In this arrangement, the track data already ripped to the hard disk isnot duplicated in recording during the CD synchronized rippingoperation.

Since the unrecorded track data only is replayed and output during theactual CD synchronized ripping operation, the CD synchronized rippingoperation is finished earlier than in the conventional art if rippedtrack data is present.

The present embodiment not only avoids useless duplication of the rippedfile, but also reduces the time required for CD synchronized ripping(performs the ripping operation at a high speed). Operations required toavoid duplication and to achieve high-speed ripping, such as therecognition of the unrecorded track and the replay of the unrecordedtrack only, are all automatically performed. The user is thus freed fromthe troublesome operation and steps.

4. Ripping State Display

As already illustrated in FIGS. 2( b) and 2(e), the CD section 2 alsonotifies the user interface section 4 of the ripping state of the trackdata corresponding to the CD(A). Upon receiving the notification of theripping state as illustrated in FIG. 2( e), the user interface section 4presents a ripping state display on the display unit 35.

FIG. 3A through FIG. 3D illustrate display examples of the ripping statedisplay presented on the display unit 35. The ripping state displayvisually presents what percent of all tracks (data) recorded on thecurrently loaded rip source CD is already ripped to the hard disk 20.

A ripping state display bar 40 is presented as the ripping state displayas shown in FIG. 3A. The ripping state display bar 40 has thelongitudinal direction thereof extending horizontally because thedisplay unit 35 is mounted on the case of the ripping system apparatus 1with the longitudinal direction of the display screen thereof alignedwith the horizontal direction.

In this case, an album title display 42 is also presented on the displayscreen. The album title display 42 accounts for the content of the textdata of the album title stored in the ripping database 20B having astructure to be discussed later.

The display status of the ripping state display bar 40 illustrated inFIG. 3A corresponds to the case in which no track data, out of the trackdata recorded on the rip source CD, is ripped to the hard disk 20.

In contrast, if some of the track data is ripped, a ripped state displaybar 41 is shown, overwriting the ripping state display bar 40 inaccordance with the percentage of the ripped track data to the trackdata of the rip source CD as shown in FIG. 3B.

If more track data is ripped, the percentage of the ripped statusdisplay bar 41 to the ripping state display bar 40 is increasing asshown in FIG. 3C.

FIG. 3A through FIG. 3D display symbolically the ripping state using abar graph.

If all track data of the rip source CD is ripped, the ripped statusdisplay bar 41 fully overwrites the entire ripping state display bar 40as shown in FIG. 3D.

FIG. 4A through FIG. 4D illustrate another example of ripping statedisplay.

As shown in FIG. 4A, a ripping state display icon 50 is displayedinstead of the ripping state display bar 40 shown in FIG. 3A throughFIG. 3D. In this case, the ripping state is symbolically represented asan amount of record to the single disk as an album. Also in this case,an album title display 52 is displayed together with the ripping statedisplay icon 50.

The display status shown in FIG. 4A corresponds to the case in which notrack data, out of the track data recorded on the rip source CD, isripped to the hard disk 20.

Some of the track data is now ripped. The ripped status display 51having a sector of a central angle responsive to the percentage of theripped track data to all track data recorded on the rip source CD isshown in the ripping state display icon 50 as illustrated in FIG. 4Bthrough FIG. 4C.

If all track data of the rip source CD is ripped, the ripped statusdisplay 51 fully overwrites the ripping state display icon 50 as shownin FIG. 4D.

The display unit 35 in the present embodiment symbolically displays theripping state as illustrated in FIG. 3A through FIG. 3D and FIG. 4Athrough FIG. 4D. Viewing the display unit 35, the user intuitivelyrecognizes how much track data recorded on the CD loaded in the CDsection 2 as a rip source is already ripped.

The user thus visually enjoys such a symbolic display.

The displays of audio apparatuses are substantially smaller in size thanthe display screen of the personal computer. If the ripping state islisted on the audio apparatus display, legibility of the ripping statemay be degraded. The use of the symbolic ripping state display in thepresent embodiment presents the ripping state in a sufficiently legiblecondition even in the small display size thereof.

The percentage of the ripped status display bar 41 to the ripping statedisplay bar 40 shown in FIG. 3A to FIG. 3D, and the percentage of theripped status display 51 to the ripping state display icon 50 shown inFIG. 4A to FIG. 4D are considered to be based on the size of the summedripped track data to the size of the data of all tracks of the ripsource CD. In other words, the percentages are considered to be based onthe number of ripped track data to the number of all tracks of the ripsource CD.

For example, it is not always necessary that, in the actual display inFIG. 3A to FIG. 3D and FIG. 4A to FIG. 4D, the percentage of the rippedstatus display bar 41 to the ripping state display bar 40, and thepercentage of the ripped status display 51 to the ripping state displayicon 50 faithfully account for the actual percentage of the ripped trackdata to all tracks of the rip source CD.

More specifically, a display pattern for the case where no ripped trackdata is present as shown in FIG. 3A and FIG. 4A and a display patternfor the case where all track data of the rip source CD are ripped areprepared. At least one display pattern for the case where part of trackdata of the rip source CD is ripped is prepared. At least, a total ofthree display patterns depending on the percentage is prepared.

Depending on the notified ripping state, one of the prepared displaypatterns is selected, and the selected display pattern is presented onthe display unit 35.

The display pattern is at a level of determined number of levelsdepending on the ripping state. This arrangement provides the advantagethat a burden on a display control process of the UI controller 31 isreduced in comparison with precisely displaying the percentage of theripped track data to all tracks of the rip source CD. Even if theperformance of CPUs and the resolution of the display are not so high,the symbol display of the present embodiment is effectively used.

The above arrangement indicates a rough percentage of the tripped trackdata to the user. In many cases, the user just desires to know whetherno track data at all or some track data is ripped, and the abovearrangement is sufficiently practical.

5. Structure of Ripping Database

To perform the CD synchronized ripping process as the present embodimentshown in FIG. 2, the unrecorded track data out of the track datarecorded on the rip source CD must be recognized.

As already briefly discussed with reference to FIG. 2, the content ofthe TOC of the CD 10 transferred from the CD section 2 is compared withthe required content of the ripping database 20B stored in the hard disk20.

The structure of the ripping database 20B will now be discussed.

FIG. 5 illustrates the general structure of the ripping database 20B. Asshown, the ripping database 20B is composed of a ripped file table D1and album information D2.

The structure of the ripped file table D1 is illustrated in FIG. 6. Asshown, the ripped file table D1 is formed as a table that associates afile ID attached to each ripped file 20A with an address on the harddisk 20 storing the ripped file 20A represented by the file ID.

The album information D2 is management data for managing the ripped file20A by album. The album here corresponds to the CD on which the rippedfile 20A has originally been recorded.

The album information D2 has a structure illustrated in FIG. 7, forexample.

As shown, the album information D2 contains an album ID D11, a CD-TOCtable D12, a ripping state table D13, a title table D14, and data rateinformation D15.

The album ID D11 stores the value of the ID identifying the CD (album)corresponding to the album information D2. The album ID is generated bythe HDD controller 25 in accordance with a predetermined rule when thealbum information D2 is produced.

The album ID is used when the HDD section 3 manages the ripped file 20Aby album.

The ripping operation illustrated in FIG. 2 refers to the CDsynchronized ripping. In accordance with the present embodiment, thenotification of the record content of the rip source CD is exchangedbetween the CD section 2 and the HDD section 3 even when the userselects a part of the track data from the CD for ripping in an operationwhich is not the CD synchronized ripping operation. In other words, theinformation content of the TOC read from the rip source CD istransferred.

The CD-TOC table D12 is generated based on the information content ofthe TOC that is transferred from the CD section 2 to the HDD section 3when a CD having none of the track data thereof ripped is replayed forripping for the first time as a rip source CD. As long as the CD isripped to the hard disk 20 for the first time, the CD-TOC table D12 isgenerated regardless of whether the ripping operation is the CDsynchronized ripping or another ripping operation.

The CD-TOC table D12 has the content directly accounting for the TOCcontent recorded on the rip source CD as shown in FIG. 19, and has thestructure illustrated in FIG. 8, for example.

The CD-TOC table D12 illustrated in FIG. 8 includes start point areasD21.

As illustrated in FIG. 19, the TOC of the CD indicates a start point(address) for each track recorded on the disk. The content of the startpoint for each track is accounted for in the start point area D21.

As illustrated in FIG. 8 for example, the values of the start points forthe tracks Tr#1-Tr#N are stored in areas D21(1), D21(2), . . . D21(N-1),and D21(N), respectively. The areas D21(1)-D21(N) store the same valuesas the start points of track #1-track #N recorded in the TOC of the CD.

The values stored in the areas D21(1)-D21(N) may be represented by MIN,SEC, and FRAME in the same way as in the TOC of the CD.

The track number of a first track is stored in an area D22 in successionto the start point area D21. The value to be stored in the area D22 maybe the track number of the first track of the disk illustrated in FIG.19.

The track number of a last track is stored in a succeeding area D23. Thevalue to be stored in the area D23 may be the track number of the lasttrack of the disk illustrated in FIG. 19.

The last area D24 indicates the value of the start point of a lead-outtrack by MIN, SEC, and FRAME as in the CD-TOC. The start point of thelead-out track also accounts for the value of the start point of alead-out track recorded in the TOC of the CD.

In succession, the ripping state table D13 is discussed.

The ripping state table D13 is a table where each track (namely, a trackrecorded in a rip source CD) belonging to the album managed by currentalbum information is associated with track data recorded on the harddisk 20 as the ripped file 20A.

In the structure of the ripping state table D13 as shown in FIG. 9, thetrack number of a track managed by the TOC on the rip source CD isassociated with the file ID of the ripped file 20A.

If the track data of the rip source CD to which the current albuminformation is considered to correspond is already recorded as theripped file 20A, the file ID of the ripped file 20A is associated withthe track number of the CD, and is then stored in the ripping statetable D13.

As shown in this figure, the file ID is represented by [“xxxxh”] (hrepresents a hexadecimal format), but a real value of the file ID isstored in practice. A row of a file ID corresponding to a track numbernot associated as being unrecorded is represented by [“----”], butconsecutive values of 00h (all 0's) or FFh (all 1's) are stored there inpractice.

The file ID here is identical to the file ID that is attached to eachripped file 20A and has already been discussed with reference to theripped file table shown in FIG. 6.

The title table D14 is an area where the title of an album and the tracktitle of the track belonging to the album are stored using text data.

The title table D14 has a structure as shown in FIG. 10, for example.The title table D14 contains an album title area D31 where the text dataas an album title is stored.

The album title area D31 is followed by a track title area D32. Thetrack title area D32 is partitioned into areas D32(1)-D32(N) storingtext data of the track titles of the tracks Tr#1-Tr#N.

If the text data of the album title has been acquired, the text data isstored in the album title area D31.

If the text data of the track title of the ripped track data is acquiredwith the ripped track data present as the ripped file 20A, the text datais stored in the area, corresponding to the track number of the trackdata, from among the areas D32(1)-D32(N) of the track title area D32.

Text information of the album title and the track title to be stored inthe title table D14 are acquired in the following manner.

If the rip source CD has a record of the text data of the album titleand the track title at the time of a ripping operation, the text decoder13 in the CD section 2 decodes and acquires the text data. In this case,the CD controller 14 transfers the acquired text data of the album titleand the track title to the HDD section 3. The HDD controller 25 in theHDD section 3 stores the in-coming text data of the album title and thetrack title in the title table D14.

If the rip source CD has no record of the text data of the album titleand the track title, a tentative album title and a tentative track titleare stored in the following manner during the ripping operation.

As for the album title, the HDD controller 25 produces the tentativealbum title in accordance with a predetermined rule, and stores theproduced album title in the album title area D31.

As for the track data, which will be discussed in detail later, the HDDcontroller 25 produces, as the text data, the track number of the albumcorresponding to the ripped file 20A ripped this time. The HDDcontroller 25 stores the text data in the area, corresponding to anappropriate track number, from among the areas D32(1)-D32(N) of thetrack title area D32.

The data rate information D15 (see FIG. 7) in the album information D2contains information representing a data rate set for the album. Thedata rate is the one for the audio data obtained subsequent to thecompression process of the signal processor circuit 22 in the HDDsection 3.

In the present embodiment, the user may modify the data rate, at whichthe signal processor circuit 22 compresses the audio data, by operatingthe operation unit 34.

The data rate must be common to all track data (ripped files 20A) withinunit of album managed by the album information D2 in accordance with thepresent embodiment. For example, if a given single piece of track data,recorded on the same rip source CD, is set to a different data rate andis recorded as a ripped file 20A on the hard disk 20, that ripped file20A, even from the same track data, is managed as a different album.

6. Process of CD Synchronized Ripping

The process for performing the CD synchronized ripping operation inaccordance with the above-referenced present embodiment will now bediscussed.

The process is discussed with reference to a flowchart illustrated inFIG. 11. The process corresponds to the operation discussed withreference to FIGS. 2( a), 2(b), and 2(c).

The HDD section 3 learns the ripping state corresponding to the ripsource CD in the course of the loading the CD as a rip source into theCD section 2 and the transfer of the content of the TOC from the CDsection 2 to the HDD section 3. The process also corresponds to theoperation to the ripping state displaying of the user interface section4 in response to the ripping state learned by the HDD section 3.

FIG. 11 also illustrates the operations of the CD section 2, the HDDsection 3, and the UI controller 31. The process of the CD section 2 isexecuted by the CD controller 14. The process of the HDD section 3 isexecuted by the HDD controller 25.

In the algorithm illustrated in FIG. 11, in a process step in step S101,the CD section 2 waits on standby until the CD 10 is loaded as a ripsource. If it is determined that the CD 10 is loaded, the algorithmproceeds to step S102.

In step S102, the TOC is read from the loaded disk, and is held in theRAM 16. In a process step in step S103, the loading of the CD 10 isnotified of.

In step S201, the HDD section 3 waits on standby for the reception ofthe notification information, notifying of the loading of the CD, sentin step S103. If the notification information is received, the algorithmproceeds to step S202. The HDD section 3 requests the TOC of thecurrently loaded CD 10 from the CD controller 14 in the CD section 2through the system bus 37.

Upon receiving the request for the TOC, the CD controller 14 performs aprocess step in step S104. In step S104, the CD controller 14 reads theTOC that has been held in the RAM 16 in the process step in step S102,and transfers the read TOC to the HDD controller 25 through the systembus 37.

In a process step in step S203, the HDD section 3 (HDD controller 25)receives the TOC thus transferred. The content information of the TOCthus received is held in the RAM 24.

In a succeeding step S204, the content of the TOC held in the RAM 24 ischecked against the CD-TOC table in the album information D2corresponding to the TOC in the ripping database 20B stored in the harddisk 20. More specifically, the HDD section 3 searches for the CD-TOCtable matching the content of the TOC held in the RAM 24. In a processstep in a succeeding step S205, the result of check is held in the RAM24.

If the CD-TOC table matching the content of the TOC held in the RAM 24is present, the album ID D11 of the album information D2 that stores theCD-TOC table is held as the check result. If the CD-TOC table matchingthe content of the TOC held in the RAM 24 is not present, apredetermined value indicating no presence of match is held as the checkresult.

The HDD section 3 uses the check result to recognize the ripped trackdata out of the track data corresponding to the rip source CD at thestart of the CD synchronized ripping as will be discussed later withreference to FIG. 12.

In succession, the HDD section 3 performs a process step in step S206.

In a succeeding step S206, the HDD section 3 references the check resultheld in the RAM 24, thereby determining whether the album information D2corresponding to the TOC received and held (namely, the currently loadedrip source CD) is present (registered in the ripping database 20B).

If an affirmative answer is obtained in step S206, at least one of trackdata recorded on the rip source CD currently loaded in the CD section 2is already recorded on the hard disk 20 as a ripped file 20A. In thiscase, the algorithm proceeds to a process step in step S207.

In step S207, the HDD section 3 searches the ripping database 20B storedin the hard disk 20 for the album information D2 corresponding to therip source CD loaded in the CD section 2. This searching may beperformed using, as a search condition, the album ID held in the RAM 24as the check result obtained in step S205.

If the album information D2 is found in the searching, the HDD section 3reads the text data of the album title stored in the album title areaD31 in the title table D14 stored in the album information D2. The HDDsection 3 also reads the ripping state table D13. In a succeeding stepS208, the text data of the read album title is transferred to the UIcontroller 31. Based on the read ripping state table D13, the HDDsection 3 produces percentage information indicating the percentage ofthe ripped track data to all tracks of the CD loaded in the CD section2, and transfers the percentage information to the UI controller 31through the system bus 37.

If a non-affirmative answer is obtained in step S206, the algorithmproceeds to step S209. The non-affirmative answer in step S206 meansthat none of the track data recorded in the rip source CD loaded in theCD section 2 is ripped and recorded at all on the hard disk 20.

In step S209, the HDD section 3 notifies of the ripping state, tellingthat the track data corresponding to the CD loaded in the CD section 2is all unrecorded. In this case, the text data of the tentative albumtitle produced in the HDD section 3 may be sent. In this way, thedisplay unit 35 tentatively displays the album title in the album titledisplay 42 (or 52).

In step S301, the UI controller 31 receives the text data of the albumtitle and the percentage information of the ripping state, bothtransferred by the HDD section 3 in step S208. Alternatively, the UIcontroller 31 may receive information notified of by the HDD section 3in a process step in step S209.

If any of the above information is received in step S301, the algorithmproceeds to step S302. In response to the received information, the UIcontroller 31 controls display control of the display unit 35 so thatthe ripping state display shown in FIGS. 3A-3D or FIGS. 4A-4D ispresented together with the album title display (42 or 52).

The process of the CD synchronized ripping operation that startssubsequent to the end of the process illustrated in FIG. 11 is discussedwith reference to a flowchart illustrated in FIG. 12. Referring to FIG.12, the operations of the CD section 2 (CD controller 14) and the HDDsection 3 (HDD controller 25) are shown.

In the process shown here, the HDD section 3 determines in step S401whether a command to start the CD synchronized ripping is obtained.

If an operation to perform the CD synchronized ripping is performed onthe operation unit 34, and the UI controller 31 receives the operationalinformation, a command to start the CD synchronized ripping is sent,through the system bus 37, to the HDD controller 25 in the HDD section 3and the CD controller 14 in the CD section 2.

If the HDD controller 25 determines in step S401 that the command tostart the CD synchronized ripping is obtained, the process in step S402and in subsequent steps is executed.

In step S402, the HDD section 3 references the check result that is heldin the RAM 24 in step S205 as illustrated in FIG. 11. In a succeedingstep S403, the HDD section 3 determines the current ripping state of theCD (album) now loaded in the CD section 2 based on the referenced checkresult.

If already ripped track data is present, the RAM 24 holds, as the checkresult, the album ID of the album information D2 corresponding to the CDloaded as a rip source in the CD section 2. The ripping database 20B isthus referenced for the content of the ripping state table D13 stored inthe album information D2 having that album ID. The HDD section 3determines whether all track data of the rip source CD is ripped orwhether a portion of the track data remains unripped.

If the RAM 24 holds, as the check result, the value indicating that alltrack data of the current rip source CD remains unripped, it isdetermined that all track data of the rip source CD are still in anunripped state.

If the determination result in step S403 is that a portion of the trackdata is in an unripped state, the algorithm proceeds to step S406.

In step S406, the album information D2 to be ripped is set. The settingof the album information D2 to be ripped is to determine albuminformation D2 the content of which must be updated in the CDsynchronized ripping operation this time.

Some tracks remain unripped in this case. In other words, the remainingtracks are already ripped, and the album information corresponding tothe CD currently loaded as the rip source in the CD section 2 is alreadypresent in the hard disk 20. In step S406, the album information storedin the ripping database 20B is set as the album information to beripped, in accordance with the CD currently loaded as the rip source inthe CD section 2.

More specifically, the album information D2 having the album ID, whichis held in the RAM 24 as the check result in step S205 shown in FIG. 11,is set to be the album information to be ripped.

Subsequent to the process step in step S406, a process step in step S407is performed.

If it is determined in step S403 that all tracks remain unripped, thealgorithm proceeds to step S404.

In step S404, new album information D2 is registered in the rippingdatabase 20B. In this case, information that may be produced as the newalbum information D2 is stored.

More specifically, a value as the album ID is produced in accordancewith a predetermined rule, and is stored as the album ID D11. The CD-TOCtable D12 is produced using the information of the TOC that is held inthe previous step S203.

For the ripping state table D13, the area of the track numbercorresponding to the file ID is reserved based on the information of theTOC. For the title table D14, the area of, at least, the album titlearea D31 and the track title areas D32(1)-D32(N) of the respective trackdata is reserved.

For the data rate information D15, the value of the data rate set at thestart of the operation of the CD synchronized ripping may be stored.

If the registration of the new album information D2 is completed in stepS404, the algorithm proceeds to step S405.

In step S405, the album information D2 to be ripped is set. Here, thealbum information D2 newly registered in step S404 is set to be ripped.The algorithm proceeds to step S407.

The data rate information D15 illustrated in FIG. 7 is stored for thealbum information D2. As already discussed in connection with the datarate information D15 with reference to FIG. 7, the data rate representedby the data rate information D15 is common to the ripped files 20A(track data) belonging to the album information. In other words, tracksfrom the same rip source CD, if ripped at different data rates, aremanaged as different albums. The hard disk 20 allows a plurality ofalbums different in data rate to be present on the hard disk 20 even ifthe albums are derived from the same rip source CD.

The data rate information D15 in the album information D2 is alsoreferenced in step S403 for the determination of the ripping state ofthe album and in step S406 for the setting of the album information tobe ripped.

Even if the album information ripped from the track data of the ripsource CD this time is present in step S403, all tracks are determinedas being unripped if the data rate indicated by the data rateinformation D15 in the album information D2 is different from the datarate set in the CD synchronized ripping this time. The algorithm thenproceeds to step S404.

In the process sequence from step S403 to step S406, the albuminformation to be set for ripping in step S406 is the album informationhaving the data rate information D15 storing the same value as the datarate set in the CD synchronized ripping this time.

In step S407, the track data not yet ripped in the current album isrecognized by referencing the ripping state table D13 of the albuminformation D2 set for ripping in a process step in step S405 or stepS406. In this way in step S407, through the system bus 37, the HDDsection 3 notifies the CD section 2 what track number the unrecordedtrack data recognized by referencing the ripping state table D13 has.For example, the HDD section 3 produces and sends a list of tracknumbers of unrecorded track data. For clarification of the discussion,the list of all track numbers is transferred in the process step in stepS407 performed subsequent to the process step in step S406.

As in the process step of the HDD side in S401, in step S501, the CDsection 2 waits on standby until a command to start the CD synchronizedripping is provided. As already discussed, the command to start the CDsynchronized ripping is issued by the UI controller 31 in response tothe operation performed by the user on the operation unit 34. Uponreceiving the command, the CD section 2 proceeds to a process step instep S502.

In step S502, the CD section 2 waits on standby for the reception of theinformation of the list of the track numbers of unrecorded (unripped)track data, notified of by the HDD section 3 in the process step in theprevious step S407. Upon receiving the notification, the CD section 2proceeds to a process step in step S503.

In step S503, the CD section 2 registers a replay program based on thenotification received in the above step S502 so that the unrecordedtrack only is replayed, and proceeds to step S504.

In step S504, the CD section 2 executes the track replay on the loadedCD 10 in accordance with the program registered in the above step S503.In a process step in a succeeding step S505, the CD section 2 performs acontrol process to transfer the audio data replayed from the CD 10 tothe signal processor circuit 22 of the HDD section 3.

The replay process of the CD 10 in step S504, and the transfer processof transferring the replayed data in step S505 are continued as asucceeding step S506 until the completion of replay is determined. Thecompletion of replay means that both the program replay and the transferof the replay data are completed.

If the completion of replay is determined in step S506, the algorithmproceeds to step S507. The CD section 2 notifies the HDD controller 25in the HDD section 3 of the completion of the replay.

In step S408, the HDD section 3 performs a control process to record thereplayed data, transferred to the signal processor circuit 22 from theCD section 2 in the previous step S505, onto the hard disk 20 to managethe replayed data by a unit of the ripped file 20A.

More specifically, the signal processor circuit 22 performs a controlprocess to compress the transferred audio data at a designated datarate. Since the compressed audio data is the data that is originallymanaged by track, the HD driver 21 is controlled so that a single pieceof track data is managed as a single ripped file 20A on a file system inthe recording of the data onto the hard disk 20.

The process step in step S408 is continued until the notification of thecompletion of the replay, to be sent by the CD section 2 in the previousstep S507, is received in step S409. When the notification of thecompletion of the replay is received in step S409, the algorithmproceeds to step S410.

After verifying that the recording of the audio data transferred fromthe CD section 2 onto the hard disk 20 is completed, the HDD section 3performs a required recording end process in step S410, and proceeds tostep S411. As for the recording end process in step S410, the HDDsection 3 may also output the notification of the end of the CDsynchronized ripping to the UI controller 31. Upon receiving thenotification, the UI controller 31 executes a control process on thedisplay unit 35 to display the end of the CD synchronized ripping. Inthis way, the user visually recognizes the end of the CD synchronizedripping.

In step S411, the ripped file table D1 and the album information D2 setfor ripping are updated in accordance with the result of the CDsynchronized ripping this time.

More specifically, information that associates the file ID of the rippedfile 20A newly recorded in this CD synchronized ripping operation withthe address on the hard disk 20 is added to the ripped file table D1.

The file ID of the ripped file 20A newly recorded in this CDsynchronized ripping operation is stored with an appropriate tracknumber of the ripping state table D13 associated therewith.

The text data of the track title of the ripped file 20A newly recordedin this CD synchronized ripping operation is stored with the track titlearea (D32(1)-D32(N)) of the appropriate track number of the title tableD14 associated therewith. A specific process for storing the track titlein accordance with the present embodiment will be discussed later withreference to FIG. 13.

When the process step in step S411 is performed as discussed above, thealgorithm proceeds to step S412. In a process step in step S412, rippingstate data (the information of percentage of the ripped tracks to alltracks of the album) responsive to the content of the ripping statetable D13 of the album information D2 updated in the above step S411 issent to the UI controller 31.

The process of the UI controller 31 that has received the ripping statedata remains unchanged from the process in steps S301 and S302 alreadyshown in FIG. 11.

With the CD synchronized ripping performed, all track data belonging tothe album are now in a ripped state. For this reason, the ripping statedisplay presented on the display unit 35 based on the ripping state databecomes a display in which all track data as the album is ripped asshown in FIG. 3D and FIG. 4D.

If it is determined in the previous step S403 that all track databelonging to the album corresponding to the currently loaded rip sourceCD is ripped, a process step in step S413 is performed.

In step S413, the HDD section 3 notifies the CD controller 14 that alltracks of the album are ripped. The CD section 2 stops the operationcorresponding to the CD synchronized ripping in response to thereception of the notification, although the process step is not shown.The notification may be output to the UI controller 31. Since all tracksare ripped, the UI controller 31 performs display control on the displayunit 35 to notify that the CD synchronized ripping operation is notexecuted. In this case, the CD synchronized ripping operation isregarded as being immediately terminated, and a display notifying of theend of the CD synchronized ripping may be immediately presented on thedisplay unit 35.

It has already been discussed that, in the present embodiment, the textdata of the track title of the track data (ripped file 20A) newlyrecorded on the hard disk 20 is stored in the title table D14 within thealbum information D2 in the process in step S411 illustrated in FIG. 12.The HDD controller 25 performs that process as illustrated in FIG. 13.

As shown, the HDD controller 25 requests the text data of the tracktitle from the CD controller 14 in the CD section 2 in a process step instep S801. In this case, the CD controller 14 requests the track titlecorresponding to the track number of the track data (ripped file 20A)newly recorded on the hard disk 20 in the course of this CD synchronizedripping process.

As already discussed with reference to FIG. 1, the CD section 2 havingthe text decoder 13 therewithin decodes a sub code to demodulate textdata if there is the text data recorded on the CD through sub coding,and stores the demodulated text data in the RAM 16.

If the RAM 16 stores the data of the track title of the track data(track number) requested in the process step in the above-mentioned stepS801, the CD controller 14 reads the data of the track title from theRAM 16, and transfers the data of the track title to the HDD controller25. If no data of the track title is stored in the RAM 16, the CDcontroller 14 transfers, to the HDD controller 25, a response indicatingthat a transfer of the data is impossible because of no data availablein the RAM 16.

In response to the process step of the CD controller 14, the HDDcontroller 25 determines in step S802 whether the text data of the tracktitle has been acquired from the CD section 2.

If the answer in step S802 is affirmative, the algorithm proceeds tostep S803. In step S803, the text data of the acquired track title isassociated with and stored onto a track title area (D32(1)-D32(N)) of anappropriate track number in the title table D14. In this way, the tracktitle, such as a specific title of a musical composition, about theripped track data is automatically registered in the ripping database20B.

If the answer in step S802 is non-affirmative as being that the textdata of the track title is not recorded on the rip source CD, thealgorithm proceeds to step S804.

In step S804, the HDD controller 25 produces text data representing thetrack number of the track data ripped this time. For example, if thetrack number of the track data ripped this time is track Tr#1, the HDDcontroller 25 produces text data [track 1] to indicate the track Tr#1.If a plurality of pieces of tack data is ripped this time, the HDDcontroller 25 produces the text data of the track numbers of all trackdata.

In step S805, the text data of the track number, produced in step S804,is treated as a track title, and is associated with and stored onto thetrack area (D32(1)-D32(N)) of an appropriate track number of the titletable D14.

In this case, a specific title, such as the title of a musicalcomposition, is not registered. The track number is still presented as atrack title different from the case in which no track title is presentat all. For example, when the track title is displayed to replay andoutput the ripped file 20A or to display a replay list, the track numberis displayed. The user recognizes the file much more easily than thecase in which no title is presented at all.

7. Cooperative Operation with Download Server

With the network interface 36 incorporated, the ripping system apparatus1 of the present invention is connectable to a network. Using thenetwork connection function, the ripping system apparatus 1 downloadsdigital audio data as a musical composition from a predetermineddownload server present in the same network, and stores the digitalaudio data in the hard disk 20 as a ripped file 20A.

A cooperative operation of the ripping system apparatus 1 of the presentembodiment with the download server is discussed below.

FIG. 14 illustrates the structure of a download server 100 that isconnected to the ripping system apparatus 1 of the present embodimentthrough the network.

As shown, the download server 100 shown here includes a storage unit101, a controller 105, and a network interface 106, mutually connectedto each other through a system bus.

The storage unit 101 includes a large capacity hard disk, for example.As shown, the storage unit 101 stores a download audio data group 102, adownload CD-TOC data group 103, and an application program 104.

A number of pieces of audio data, stored to be downloaded, in the formof database are stored as the download audio data group 102. Each audiodata constituting the download audio data group 102 is compressed usingthe same compression method of the ripped file 20A in the presentembodiment. It is contemplated that a compression process is performedon uncompressed audio data when the uncompressed audio data is recordedas the ripped file 20A subsequent to downloading. To save time requiredfor downloading, compressing beforehand the download audio data ispreferable and widely accepted.

The download CD-TOC data group 103 is arranged in the form of databasein which the TOC data having the same content as the one recorded on thealbum as the CD is recorded on each of a number of albums.

Audio data forming the download audio data group 102 is track dataactually recorded on the CD as any album. The download CD-TOC data group103 is formed of the CD-TOC corresponding to the album (CD) to which theaudio data (track data) forming the download audio data group 102belongs.

The application program 104 is formed of a variety of programs thecontroller 105 must execute.

The controller 105 performs a variety of required processes to executethe functions as a download server based on the application program 104stored in the storage unit 101.

The network interface 106 is arranged to connect the download server 100to the network. The download server 100 is thus connected to andcommunicates with a plurality of ripping system apparatuses 1 present ina remote place through the network.

The structure of the ripping system apparatus 1 illustrated here hasbeen discussed, and is connected to the download server through thenetwork interface 36 and the network shown in FIG. 1.

A download operation executed between the download server 100 thusconstructed and the ripping system apparatus 1 is performed as discussedbelow.

The user of the ripping system apparatus 1 connects the ripping systemapparatus 1 to the download server 100 through the network by performinga predetermined operation on the display unit 35. In this case, the UIcontroller 31 issues, to the HDD controller 25, a connection request forconnection with the download server 100 in response to the connectionoperation for connection with the download server 100 performed on thedisplay unit 35.

Communication control using the network interface 36 may be performed byany of the CD controller 14, the HDD controller 25, and the UIcontroller 31. Here, the HDD controller 25 has the responsibility toperform the communication control.

In response to the input of the connection request, the HDD controller25 establishes connection with the network through the network interface36, and executes control process to access an address (URL (UniformResource Locator)) of the download server 100 over the network. In thisway, the ripping system apparatus 1 is now in the connected conditionthereof to the download server 100 through the network.

Under this condition, the download server 100 can send list informationof the download audio data to the ripping system apparatus 1. The listinformation has the structure in which a list item of downloadable audiodata is associated with a data ID of that audio data. The ripping systemapparatus 1 displays the received and acquired list information on thedisplay unit 35 as a download list. Alternatively, the download list maybe displayed on a connectable external display device, although notshown in FIG. 1.

For example, the user of the ripping system apparatus 1 selects anddesignates the audio data to be downloaded, and performs an operation todownload the designated audio data by performing a GUI operation on thereplay list displayed as discussed above. As in the process shown inFIG. 15, the ripping system apparatus 1 executes a download operation todownload the audio data from the download server 100 in response to theoperation.

The download operation will be discussed with reference to a flowchartillustrated in FIG. 15. The flowchart illustrated in FIG. 15 covers theprocesses of the ripping system apparatus 1 and the download server 100.

The process of the ripping system apparatus 1 may be executed by any ofthe CD controller 14, the HDD controller 25, and the UI controller 31,as appropriate. The communication control process through the networkinterface 36 is executed by the HDD controller 25, as already discussed.

The process of the download server 100 is performed by the controller105.

When the operation to execute the downloading process is performed onthe operation unit 34 in the ripping system apparatus 1 as discussedabove, the UI controller 31 recognizes the operation. The UI controller31 extracts the data ID of the audio data, designated for downloading,from among IDs contained in the list information. The UI controller 31outputs a command to execute the downloading process together with thedata ID to the HDD controller 25.

In response to the input command, the HDD controller 25 performs acontrol process to send a download request to the download server 100 ina process step in step S601. More specifically, the HDD controller 25produces download request information, and sends, to the networkinterface 36 through the system bus 37, the produced download requestinformation together with the data ID of the audio data to bedownloaded. The HDD controller 25 performs a control process to send thedownload request information containing the data ID to the downloadserver 100 through the network interface 36.

In step S701, the download server 100 waits on standby until thedownload request information sent from the ripping system apparatus 1 isreceived. Upon receiving the download request information, the downloadserver 100 proceeds to step S702.

In step S702, the download server 100 searches the download audio datagroup 102 stored in the storage unit 101 for the audio data in responseto the received download request information. For example, the downloadserver 100 searches for the audio data matching the data ID contained inthe received request information.

As already discussed, each audio data constituting the download audiodata group 102 has the same content recorded as the track data in anyCD. The TOC concerning the CD that has recorded the audio data of thedownload audio data group 102 is stored in the download CD-TOC datagroup 103. A pointer to the CD-TOC having the record of the audio datais attached to the audio data forming the download audio data group 102.

If the audio data is searched in the download audio data group 102 instep S702, the pointer to the CD-TOC attached to the searched audio datais referenced, and the CD-TOC indicated by the referenced pointer issearched in the download CD-TOC data group 103.

In the process step in step S702, the download server 100 searches forthe audio data requested by the ripping system apparatus 1 and theCD-TOC identical to the TOC recorded on the CD that has recorded theaudio data.

In step S703, the download server 100 performs a control process totransfer the audio data and the CD-TOC, acquired in the searching in theabove-mentioned step S702, to the network interface 106, therebydesignating the address (an IP address, for example) of the requestingripping system apparatus 1 to request the ripping system apparatus 1 tosend the address. In this way, the information of the audio data and theCD-TOC is sent to the requesting ripping system apparatus 1 through thenetwork as download data.

After sending the download request in the previous step S601, theripping system apparatus 1 waits on standby until the download dataresponsive to the download request is received in step S602. Uponreceiving the download data, the ripping system apparatus 1 proceeds tostep S603.

In step S603, the ripping system apparatus 1 determines whether theCD-TOC data contained in the received and acquired download data hasbeen registered as the album information D2 in the ripping database 20Bstored in own hard disk 20. In other words, the ripping system apparatus1 determines whether the album information D2 having the CD-TOC data(the content of the album) identical in content to the CD-TOC dataacquired as the download data is present. In the determination process,the ripping system apparatus 1 checks the CD-TOC table D12 stored ineach of the album information D2 stored in the hard disk 20 against thecontent of the received and acquired CD-TOC for matching. If a match isfound, the CD-TOC data is already registered. If no match is found, theCD-TOC data is not yet registered.

In the above case, a determination process is also performed on the datarate.

More specifically, even if the CD-TOC received as the download data isidentical to the content of the CD-TOC table D12 of the CD section 2,the album information is not considered as matching if the valueindicated by the data rate information D15 stored in the albuminformation D2 is different from the value of the data rate set in theaudio data as the download data. In other words, that CD-TOC isprocessed as not yet registered as the album information D2.

If the determination result in step S603 is that the TOC data receivedas the download data is not yet registered as the album information D2,the algorithm proceeds to step S604.

In step S604, new album information D2 is produced using the CD-TOCinformation of the download data received and acquired in the previousstep 602, and is stored in the ripping database 20B. In step S605, thenewly produced album information D2 is set as album information D2 of adownload destination (for ripping). The algorithm then proceeds to stepS607.

If the determination result in step S603 is that the TOC data receivedas the download data is registered as the album information D2, thealgorithm proceeds to step S606.

In a process step in step S606, the album information D2 registered andalready stored in the ripping database 20B is set as album informationD2 of a download destination (for ripping). The algorithm proceeds tostep S607.

In step S607, the audio data, received and acquired as the download datain the process step in the previous step S602, is recorded onto the harddisk 20 as the ripped file 20A. In this case, since the audio data asthe download data is audio data already compressed using the same methodas the one used in the ripped file 20A, the compression process of thesignal processor circuit 22 is not required.

When the recording of the audio data is completed in the above stepS607, the ripped file table D1 is updated based on the result ofrecording so that the audio data recorded on the hard disk 20 as theripped file 20A this time is registered.

Along with this step, the content of the album information D2 set as thedownload destination (for ripping) in the previous step S605 or S606 isupdated. More specifically, the file ID of the ripped file 20A newlyrecorded in this downloading is stored in association with anappropriate track number of the ripping state table D13.

When the ripped file 20A as the download data is associated with thetrack number of the ripping state table D13, the HDD controller 25 mustknow the track number of the audio data as the download data in thealbum. To this end, attaching the information of the track number withinthe album to the audio data as the download data suffices.

The following arrangement is contemplated for the HDD controller 25 torecognize the track number of the audio data as the download data withinthe album.

Specifically, replay time of the audio data is determined from the sizethereof. Replay time of each track within the album is also determinedfrom the content of the CD-TOC acquired as the same download data. Thereplay time of the audio data is checked against the replay time of eachtrack obtained from the CD-TOC. If the replay times match each other,the HDD controller 25 recognizes the track number.

Since the ripped file 20A is downloaded from the download server 100rather than the CD in this case, the ripping system apparatus 1 isunable to acquire the text data of the track title.

In this case, the track title of the track number in text data isproduced in accordance with the process of step S804→S805 in theflowchart shown in FIG. 13. The track title is associated with andstored to the track area (D32(1)-D32(N)) of an appropriate track numberof the title table D14.

The track title recorded as the text data on each CD (CD-TOC)corresponding to download audio data may be stored in the form of adatabase in the storage unit 101 of the download server 100, forexample.

In addition to the audio data and the CD-TOC data, the download server100 sends the text data of the track title as the download data inresponse to the download request. In this way, the ripping systemapparatus 1 acquires the track title during downloading, thereby storingthe track title in the title table D14 of the album information D2. Ifthe download data includes the album title in addition to the tracktitle, the album title is also stored in the title table D14.

In the process illustrated in FIG. 15, the download server 100 alwayssends the CD-TOC when the download server 100 downloads the audio datain response to the download request. The ripping system apparatus 1determines whether the received and acquired CD-TOC has already beenregistered as the album information. If the CD-TOC has been registered,the received and acquired CD-TOC is unused and discarded.

The following downloading method for downloading the CD-TOC may becontemplated.

When the audio data to be downloaded is selected and determined from thedownload list in the ripping system apparatus 1, the ripping systemapparatus 1 determines whether the album information D2 corresponding tothe selected and determined audio data is registered in the rippingdatabase 20B of the hard disk 20.

To this end, an arrangement must be prepared to recognize contentidentity as to whether the audio data presented in the download list andthe audio data recorded as the ripped file 20A on the hard disk 20 areidentical to each other in content. In one arrangement, a file ID, whichbecomes unique with the same rule applied thereto, is attached to theaudio data in the download list and the ripped file 20A.

For example, both the audio data in the download list and the rippedfile 20A are originally the same audio data recorded on the CD. The fileID may be obtained by calculating a predetermined function on data suchas the TOC and the track number of the CD that records that audio data.The audio data of the same track number on the same CD is tagged withthe identical value of file ID on both the download server 100 and theripping system apparatus 1.

If it is determined that the album information D2 corresponding to theaudio data selected and determined from the download list has beenregistered in the ripping database 20B of the hard disk 20, the rippingsystem apparatus 1 does not need to acquire the CD-TOC from the downloadserver 100. In such a case, the ripping system apparatus 1 and thedownload server 100 operate so that only the audio data as the downloaddata is downloaded. Since the download data is the audio data only, thesize of the download data becomes smaller. For example, download time isshortened, and the burden on transmitter and receiver sides forprocessing the download data is reduced.

If it is determined that the album information D2 corresponding to theaudio data selected and determined from the download list has not beenregistered in the ripping database 20B of the hard disk 20, the audiodata and the CD-TOC data (and the track title and the album title) aredownloaded as the download data in the same manner as already discussed.

In accordance with the present embodiment, the CD-TOC is also acquiredand is registered as the album information D2 when the download server100 downloads the audio data.

When the ripping system apparatus 1 of the present embodiment performsthe CD synchronized ripping thereafter, the album information D2registered based on the CD-TOC acquired as the download data remainsusable.

With the CD 10 loaded in the CD section 2 for the CD synchronizedripping, the process in step S204 and subsequent steps shown in FIG. 11is performed to recognize the ripping state concerning the album as theloaded CD 10. To perform the process in step S204 and subsequent steps,the album information D2 registered based on the CD-TOC acquired as thedownload data is used without any difference from the album informationD2 registered based on the TOC read and acquired from the CD 10.

In accordance with the present embodiment, programs for the processesillustrated in FIG. 11, FIG. 12, FIG. 13, and FIG. 15, to be performedby the CD controller 14 of the CD section 2, the HDD controller 25 ofthe HDD section 3, and the UI controller 31, are stored in the ROM 15,the ROM 23, and the ROM 32 of the respective controllers. Since the HDDcontroller 25 has the hard disk 20 in the present embodiment, theprograms may be installed in the hard disk 20 rather than the ROM 23.

The program to be executed by the controller 105 of the download server100 is stored in the storage unit 101 as a hard disk, for example, asthe application program 104 is stored as illustrated in FIG. 14.

The above-mentioned programs may be stored (recorded) temporarily orpermanently in a removable storage medium such as a flexible disk, aCD-ROM (Compact Disc Read Only Memory), an MO (Magnet Optical) disc, aDVD (Digital Versatile Disc), a magnetic disc, or a semiconductormemory. Such a removable storage medium may be provided as so-calledpackage software.

For example, in the ripping system apparatus 1 of the presentembodiment, each of the CD-ROM and DVD in the CD section 2 isreplayable. The CD section 2 replays, and read programs from the CD-ROMand DVD, and stores the programs in the ROM 15, the ROM 23, the ROM 32,and the hard disk 20 for installation.

A data interface such as a USB (Universal Serial Bus) or IEEE1394 may bemounted in the ripping system apparatus 1 of FIG. 1. The programsreplayed from a medium by a medium driver connected to such a datainterface are installed in the ripping system apparatus 1 in the samemanner described above.

Programs executing processes in compliance with the processesillustrated in FIG. 11, FIG. 12, FIG. 13, and FIG. 15 may be included ina program offering ripping function, and the program may be stored ineach of a variety of storage media. The operation of the presentembodiment may be performed after installing the program in ageneral-purpose personal computer.

The program may be installed from the above-referenced removable storagemedium. Furthermore, the program may be downloaded, through a networksuch as an LAN (Local Area Network), or the Internet, from a server thatstores the program.

The present invention is not limited to the aforementioned arrangements.

For example, the aforementioned discussion of the ripping systemapparatus 1 of the present embodiment is assumed to be a singleapparatus. However, the ripping system apparatus 1 may be arranged in asystem where the ripping system apparatus 1 is separated into at leasttwo units, one unit having the function of the CD section 2 and theother unit having the function of the HDD section 3, with the two unitsinterconnected to each other through a predetermined data interface. Inthis case, the function of the user interface section 4 shown in FIG. 1may be provided in each of the unit functioning as the CD section 2 andthe unit functioning as the HDD section 3.

In accordance with the present embodiment, the digital audio data isripped. The present invention is not limited to the digital audio data.The type of data may be video data as long as the data to be ripped ismanaged by album.

The storage medium as a rip source and the storage medium as a ripdestination are not limited to the CD and the hard disk, respectively.The storage media may include a variety of storage media including otherdisk media, and a data storage medium such as a memory element.

As described above, the present invention recognizes the data unrecordedon the second storage medium (as the ripping state) out of the datarecorded on the first storage medium when the data managed by the firstmanagement data (TOC of the CD) by program (track) is read from thefirst storage medium (CD), and stored onto the second storage medium(hard disk). Based on the recognition result of the unrecorded data, thepresent invention replays and outputs the unrecorded data only, andstores the unrecorded data onto the second storage medium.

For example, data recording may performed from the first storage mediumto the second storage medium to achieve the record result that fullyaccounts for the content recorded on the first storage medium in therecord content in the second storage medium. In other words, all data onthe first storage medium is ripped to the second storage medium.

In such a case, if a portion of the data belonging to the album isalready recorded on the second storage medium, the arrangement of thepresent invention prevents already recorded portion of data from beingreplayed from the first storage medium. As a result of ripping, no datais duplicated on the second storage medium, and the capacity of thesecond storage medium is effectively used.

In accordance with the present invention, the data already recorded onthe second storage medium is not transferred from the first storagemedium to the second storage medium. Time required for ripping isaccordingly reduced when the data content on the first storage medium isripped to the second storage medium in a manner such that the recordcontent of the second storage medium fully accounts for the recordcontent of the first storage medium.

In accordance with the present invention as described above, theoperation to recognize the data unrecorded on the second storage medium(as the ripping state) out of the data recorded on the first storagemedium, and the operation to replay only the unrecorded data to beripped based on the recognition result from the first storage medium(for program replay) are automatically performed without userintervention based on the result of comparison (check) of the firstmanagement data (TOC of the CD) read from the first storage medium withthe second management data (album information) produced from the firstmanagement data. In other words, the ripping operation of the presentinvention is automatically executed without the need for user operation,and improves the ease of use of the apparatus.

1. A data recording method comprising: reading first management datafrom a first recording medium, said first management data identifyingall tracks of source data recorded on said first recording medium;comparing said first management data with second management data, saidsecond management data identifying all files of ripped data recorded ona second recording medium; determining whether any of the files of theripped data recorded on said second recording medium is recorded on saidfirst recording medium; transferring one of the tracks of the sourcedata to said second recording medium, said one of the tracks of thesource data being transferred when absent from said second recordingmedium, wherein said one of the tracks of source data on said secondrecording medium becomes one of the files of the ripped data.
 2. A datarecording method according to claim 1, wherein the step of transferringincludes: compressing said one of the tracks of the source data, andrecording the compressed one of the tracks of the source data onto saidsecond recording medium.
 3. A data recording method according to claim1, further comprising: displaying transferring status of one of thetracks of the source data.
 4. A data recording method comprising:reading first management data from a first recording medium, said firstmanagement data identifying all tracks of source data recorded on saidfirst recording medium; comparing said first management data with secondmanagement data, said second management data identifying all files ofripped data recorded on a second recording medium; determining whetherany of the files of the ripped data recorded on said second recordingmedium is recorded on said first recording medium; transferring one ofthe tracks of the source data to said second recording medium, said oneof the tracks of the source data being transferred when absent from saidsecond recording medium; displaying the percentage of said all tracks ofsource data that are recorded as the files of the ripped data.
 5. A datarecording method according to claim 4, wherein the step of transferringincludes: compressing said one of the tracks of the source data, andrecording the compressed one of the tracks of the source data onto saidsecond recording medium.
 6. A data recording apparatus comprising: acontroller configured to control reading first management data from afirst recording medium, said first management data identifying alltracks of source data recorded on said first recording medium; a secondrecording medium configured to store second management data and files ofripped data, said second management data identifying all of the files ofthe ripped data recorded on said second recording medium, wherein saidfirst management data is compared with second management data todetermine whether any of the files of the ripped data recorded on saidsecond recording medium is recorded on said first recording medium,wherein said controller controls reading one of the tracks of the sourcedata from said first recording medium, said one of the tracks of thesource data being read when absent from said second recording medium,wherein said one of the tracks of source data on said second recordingmedium becomes one of the files of the ripped data.
 7. A data recordingapparatus according to claim 6, further comprising: a processorconfigured to compress said one of the tracks of the source data, thecompressed one of the tracks of the source data being recorded onto saidsecond recording medium.
 8. A data recording apparatus according toclaim 6, further comprising: a display configured to displaytransferring status of one of the tracks of the source data.
 9. A datarecording apparatus comprising: a controller configured to controlreading first management data from a first recording medium, said firstmanagement data identifying all tracks of source data recorded on saidfirst recording medium; a second recording medium configured to storesecond management data and files of ripped data, said second managementdata identifying all of the files of the ripped data recorded on saidsecond recording medium, wherein said first management data is comparedwith second management data to determine whether any of the files of theripped data recorded on said second recording medium is recorded on saidfirst recording medium, wherein said controller controls reading one ofthe tracks of the source data from said first recording medium, said oneof the tracks of the source data being read when absent from said secondrecording medium; a display configured to show the percentage of saidall tracks of source data that are recorded as the files of the rippeddata.
 10. A data recording apparatus according to claim 9, furthercomprising: a processor configured to compress said one of the tracks ofthe source data, the compressed one of the tracks of the source databeing recorded onto said second recording medium.